Fixes # (#3583)

Problem

Currently, after a release, the main branch version remains the same as the last release (e.g., 1.22.0).
This creates ambiguity over whether a build from main is:

• A released version, or
• A development build with unreleased changes.

Changes

Proposed Solution

Automate the post-release version bump so that the main branch always reflects a development build with a -DEV suffix.

Implementation

1. New Pre-Release Workflow (.github/workflows/pre-release.yml)

   • Triggered manually before a release.
   • Removes the -DEV suffix from include/opentelemetry/version.h.
   • Commits the clean version to main.
   • Creates and pushes a version tag (vX.Y.Z).

2. New Post-Release Workflow (.github/workflows/post-release.yml)

   • Triggered automatically when a tag (vX.Y.Z) is pushed.
   • Calculates the next minor version.
   • Updates include/opentelemetry/version.h to that next version with a -DEV suffix.
   • Commits and pushes the change to main.

3. version.h Update
   Example after release of 1.22.0 → bumped to:

   // Development version after 1.22.0 release
   #define OPENTELEMETRY_VERSION "1.23.0-DEV"
   #define OPENTELEMETRY_VERSION_MAJOR 1
   #define OPENTELEMETRY_VERSION_MINOR 23
   #define OPENTELEMETRY_VERSION_PATCH 0

Benefits

• Clear separation between released versions and development builds.
• Fully automated — no manual bump required after release.
• Reduces the risk of human error in the versioning process.

Files Added:

• .github/workflows/pre-release.yml
• .github/workflows/post-release.yml

Files Updated:

• include/opentelemetry/version.h

Checklist:

• CHANGELOG.md updated for non-trivial changes
• Unit tests have been added
• Changes in public API reviewed